Code-editor agent and Debug agent prototypes by rblalock · Pull Request #286 · agentuity/cli

rblalock · 2025-05-11T01:26:00Z

✨ Experimental Debug-Agent and Code-Edit Agent

These are prototypes to demonstrate some concepts / ideas coming down the pike. I fully expect all of this to be nuked soon :-)

For now, both of these agents use the Go Anthropic SDK. You must have a ANTHROPIC_API_KEY on your path for these to work. In the future this won't be necessary but for the prototype this is an easy way to test.

Code editing agent

This runs when a new agent is created via the CLI. It will ask the user the purpose of the agent, which is used as a prompt to change the agent template accordingly. You must add the experimental flag to use it:

agentuity agent create --experimental-code-agent

Debug agent

This agent runs when running agentuity dev. It will watch logs and if there is an error or crash, etc. it will try to figure out what the problem is and debug it for you. You must add the experimental flag to use it:

agentuity dev --experimental-debug-agent

Some opinions on the state of this:

There's a balance to what parts of an agent (or multi-agents) live locally like this, and what should be in the cloud. Need to discuss.
Ideally this isn't bound to just Anthropic. For example - for error logs, we could do a pass using Groq and LLama4 for speed and cheapness, before going deeper with a beefier model (if/when needed). This means we need to abstract how some of this works.
We need to be careful how these get invoked. Just need to be smarter than this code currently is. For example - right now if there's a continuous set of errors, the debug agent will just keep chugging through them, if they're new / different.

other thoughts:

there might be multiple errors that come in at once. which should the agent focus on? maybe we should chunk them together and let it analyze a bunch in a time window?

that means we might need a more dynamic tui input, depending on if the agent wants to ask a question (like "which error should i analyze" and give a list)

realistically there could be tons of stdout between some of this agent stdout...how do we best handle? should the agent ask the user in the terminal if it should analyze, and it just doesn't show anything else until the user performs an action?

might be an argument for a TUI with tabs, one of the typical dev stuff and the other for the agent

clean up too

…out now

robindiddams

some styling stuff. and i showed you how to fix the embed

I think the reflector stuff on the anthropic tools api is okay for this pr, but we can probably use a generator to make all the correct types at compile-time and get some more safefy/speed

Also since tools/debugagent/codeagent are all kinda one unit maybe it's better to just stick them all in a subdir internal/agents/ they can still be separate modules. since tools especially is a generic sounding module and it would likely not be used outside of an agent.

robindiddams · 2025-05-15T14:28:58Z

+
+	"github.com/agentuity/cli/internal/debugagent"
+	debugmon "github.com/agentuity/cli/internal/dev/debugmon"
+
+	"github.com/agentuity/cli/internal/dev/linkify"


Suggested change

"github.com/agentuity/cli/internal/debugagent"

debugmon "github.com/agentuity/cli/internal/dev/debugmon"

"github.com/agentuity/cli/internal/dev/linkify"

"github.com/agentuity/cli/internal/debugagent"

"github.com/agentuity/cli/internal/dev/debugmon"

"github.com/agentuity/cli/internal/dev/linkify"

robindiddams · 2025-05-15T14:31:49Z

+)
+
+// NOTE: I think we should be able to use that fancy go:embed thing here
+// but the import gets nuked when we build the CLI, so doing this nasty
+// init() thing instead.
+var systemPrompt string
+
+func init() {
+	_, file, _, _ := runtime.Caller(0)
+	base := filepath.Dir(file)
+	p := filepath.Join(base, "./debug-system-prompt.txt")
+	if data, err := os.ReadFile(p); err == nil {
+		systemPrompt = string(data)
+	}
+}


you need to use a blind import:

Suggested change

)

// NOTE: I think we should be able to use that fancy go:embed thing here

// but the import gets nuked when we build the CLI, so doing this nasty

// init() thing instead.

var systemPrompt string

func init() {

_, file, _, _ := runtime.Caller(0)

base := filepath.Dir(file)

p := filepath.Join(base, "./debug-system-prompt.txt")

if data, err := os.ReadFile(p); err == nil {

systemPrompt = string(data)

}

}

_ "embed"

)

//go:embed debug-system-prompt.txt

var systemPrompt string

if your editor removes that still thats an issue with your config.

robindiddams · 2025-05-15T14:33:17Z

+)
+
+// NOTE: I think we should be able to use that fancy go:embed thing here
+// but the import gets nuked when we build the CLI, so doing this nasty
+// init() thing instead.
+var systemPrompt string
+
+func init() {
+	_, file, _, _ := runtime.Caller(0)
+	base := filepath.Dir(file)
+	p := filepath.Join(base, "./code-system-prompt.txt")
+	if data, err := os.ReadFile(p); err == nil {
+		systemPrompt = string(data)
+	} else {
+		systemPrompt = ""
+	}
+}


same here too.

robindiddams · 2025-05-15T14:34:12Z

+		return errors.New("codeagent: Dir must be provided")
+	}
+	if opts.Goal == "" {
+		return errors.New("codeagent: Goal must be provided")


inconsistent casing, errors should start lowercase

Suggested change

return errors.New("codeagent: Dir must be provided")

}

if opts.Goal == "" {

return errors.New("codeagent: Goal must be provided")

return errors.New("codeagent: dir must be provided")

}

if opts.Goal == "" {

return errors.New("codeagent: goal must be provided")

robindiddams · 2025-05-15T14:34:57Z

+		goalFlag, _ := cmd.Flags().GetString("goal")
+		agentGoal = goalFlag


not sure what foalFlag is supposed to do

Suggested change

goalFlag, _ := cmd.Flags().GetString("goal")

agentGoal = goalFlag

agentGoal, _ := cmd.Flags().GetString("goal")

robindiddams · 2025-05-15T14:41:28Z

+	trace := func(format string, args ...interface{}) {
+		if opts.Logger != nil {
+			opts.Logger.Trace(format, args...)
+		}
+	}


this is a little weird, we never optionally allow a logger, expect it and the caller can either tune the desired level or pass a logger.NewNoOpLgger

Suggested change

trace := func(format string, args ...interface{}) {

if opts.Logger != nil {

opts.Logger.Trace(format, args...)

}

}

logger := opts.Logger.With(map[string]any{"pkg":"debugagent"})

robindiddams · 2025-05-15T14:44:28Z

+			if useCache {
+				keyHash := hash(opts.Error)
+				cachePath := filepath.Join(cacheDir, keyHash+".txt")
+				_ = writeCache(cachePath, cacheEntry{Analysis: analysis})


check the error or omit _ =

robindiddams · 2025-05-15T14:44:37Z

+		if useCache {
+			keyHash := hash(opts.Error)
+			cachePath := filepath.Join(cacheDir, keyHash+".txt")
+			_ = writeCache(cachePath, cacheEntry{Analysis: analysis})


jhaynie · 2025-05-15T20:54:47Z

i think we need to hold off on merging this until after the devmode changes and also need to reconsider some of this based on conversation internally about how to reconcile the code agent and other dev agents.

rblalock · 2025-05-16T13:13:35Z

Yup makes sense. I'll close this - but at least we have some reference points for some ideas

rblalock added 21 commits May 10, 2025 15:55

first draft of a code editor

f924699

Add agent prompt flow to project creation

8a9d513

clean up too

Debug agent help

37ff113

more debug handling

096f63b

deep link, error cache hit, and more.

94d823e

clean up comments

cfd1fc6

fix error gen

e832b0d

just log a warn for now.

29f058e

Cleanup, tool refactor and organization.

51eeb72

Remove some emojis for now

40348e7

apply fixes!

d49c41d

apply patch tool fix

9100a2c

try to be careful of changes after edit

442d2b3

optimize file reading

9b0aa11

monitor should only listen on stderr, git diff is non-interactive std…

a7ede05

…out now

pass in the analysis to the fix call

023bd61

Make it more obvious the applied edits in stdout

e5a8e6b

fix test

170a75c

tell grep tool to take a chill pill. add tracing to debug agent

4f32d14

remove old test

47a6108

streaming!

ae59ba0

rblalock marked this pull request as ready for review May 14, 2025 15:15

rblalock requested review from jhaynie, pec1985 and robindiddams May 14, 2025 15:15

robindiddams suggested changes May 15, 2025

View reviewed changes

rblalock closed this May 16, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Code-editor agent and Debug agent prototypes#286

Code-editor agent and Debug agent prototypes#286
rblalock wants to merge 21 commits intomainfrom
code-editor-prototype

rblalock commented May 11, 2025 •

edited

Loading

Uh oh!

robindiddams left a comment •

edited

Loading

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

robindiddams May 15, 2025

Uh oh!

jhaynie commented May 15, 2025

Uh oh!

rblalock commented May 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

		goalFlag, _ := cmd.Flags().GetString("goal")
		agentGoal = goalFlag

	goalFlag, _ := cmd.Flags().GetString("goal")
	agentGoal = goalFlag
	agentGoal, _ := cmd.Flags().GetString("goal")

Conversation

rblalock commented May 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✨ Experimental Debug-Agent and Code-Edit Agent

Code editing agent

Debug agent

Uh oh!

robindiddams left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

jhaynie commented May 15, 2025

Uh oh!

rblalock commented May 16, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

rblalock commented May 11, 2025 •

edited

Loading

robindiddams left a comment •

edited

Loading